Systems and methods for reducing power consumption during communication between link partners

ABSTRACT

Generally, this disclosure describes an energy-efficient Ethernet communications approach. In at least one embodiment described herein, an Ethernet controller may be configured to operate in an active power state to transmit or receive data packets at a maximum available link speed. The maximum available link speed may be determined by a negotiation between the Ethernet controller and a link partner coupled to the Ethernet controller. Once the data packets are transmitted or received, the Ethernet controller may be configured to operate in an idle power state to reduce energy consumption.

FIELD

The present disclosure relates to Ethernet communications, and, moreparticularly, to energy efficient Ethernet using active/idle toggling.

BACKGROUND

Current Ethernet solutions either remain operating at a given speed,e.g. 1000BASE-T, regardless of the bandwidth utilization, and thusconsume more power than necessary, or they require software drivers todrop the link and auto-negotiate to a new, lower speed to save power,but losing link for several seconds in the process making that optionunsuitable for many applications. IEEE 802.3 Working Group has recentlyformed an Energy-Efficient Ethernet (EEE) Task Force, officially named802.3az, to define a solution for reducing the average power consumptionof Ethernet by addressing the issues noted above with current solutions.So far there have been two proposals to the IEEE Task Force for EEE,both of which recommend rate-shifting to track the bandwidth utilizationdemand. Rate-shifting, as proposed by the EEE Task Force, is a techniquewhere the Ethernet communication speed may be up-shifted ordown-shifted, depending on bandwidth demand. For example, during periodsof low demand, the speed may be shifted down from a fast communicationspeed to a slower communication speed (e.g., 1000BASE-T to 100BASE-TX).As demand increases, the speed may be shifted up.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of embodiments of the claimed subject matterwill become apparent as the following Detailed Description proceeds, andupon reference to the Drawings, wherein like numerals depict like parts,and in which:

FIG. 1 depicts a graph of power vs. time consistent with one exemplaryembodiment of the present disclosure;

FIG. 2 illustrates a system embodiment consistent with the presentdisclosure;

FIG. 3 depicts a flowchart of exemplary data transmission operationsconsistent with the present disclosure;

FIG. 4 depicts a flowchart of exemplary data reception operationsconsistent with the present disclosure;

FIG. 5A depicts a power profile graph according to a rate-shiftingEthernet communications technique; and

FIG. 5B depicts a power profile graph consistent with the presentdisclosure.

Although the following Detailed Description will proceed with referencebeing made to illustrative embodiments, many alternatives,modifications, and variations thereof will be apparent to those skilledin the art. Accordingly, it is intended that the claimed subject matterbe viewed broadly, and be defined only as set forth in the accompanyingclaims.

DETAILED DESCRIPTION

Generally, this disclosure describes an energy-efficient Ethernetcommunications approach. In at least one embodiment described herein, anEthernet controller may be configured to operate in an active powerstate to transmit or receive data packets (when available) at a maximumavailable link speed. The maximum available link speed (e.g., 1000BASE-T(GbE), 10 GBASE-T, etc.) may be determined by a negotiation between theEthernet controller and a link partner coupled to the Ethernetcontroller. Once the data packets are transmitted or received, theEthernet controller may be configured to operate in an idle power stateto reduce energy consumption. The “idle power state”, as used herein,may be defined as a power state that is sufficient to maintain an openlink with the link partner, but insufficient to transmit or receivedata. In other words, the “idle power state”, as used herein, is athreshold power consumption state that is below a power consumptionstate to transmit at least one data packet, while maintaining theEthernet communications link between the Ethernet controller and thelink partner. The “active power state”, as used herein, may include an“active data transmission power state” defined as a power state totransmit data at a maximum available link speed, and an “active datareceive power state” defined as a power state to receive data at amaximum available link speed.

FIG. 1 depicts a graph 100 of power vs. time consistent with oneexemplary embodiment of the present disclosure. In this embodiment, datapackets 102 a, 102 b, 102 c may be transmitted or received in a burstfashion at a maximum active power state 104 (e.g., a maximum availablelink speed). When data packets are available to be transmitted orreceived, an Ethernet controller (not shown in this Figure) may togglepower between an idle power state 108 and an active state 104. In thisexample, the active power state 104 is a power state associated with themaximum available data transmission or reception speed. The idle powerstate 108 is a power state that is sufficient to maintain an open linkwith the link partner, but insufficient to transmit or receive data. Theidle power state 108, in this example, represents a power consumptionthat is slightly larger than an off state 106 and significantly lowerthan the active power state 104.

During a transition from idle power state 108 to active power state 104,there may be a first delay period 110. Likewise, during a transitionbetween the active power state 104 to the idle power state 108, theremay be a second delay period 112. The idle interval 114 between packetbursts (e.g., between burst 102 a and 102 b) may be based on bandwidthconsiderations and/or the amount of data available in a data buffer.

FIG. 2 illustrates a system embodiment 200 consistent with the presentdisclosure. The system 200 includes a host system 202 and an Ethernetcontroller 220. The host system 202 may include a host processor 204,chipset circuitry 206 and system memory 208. The host processor 204 mayinclude one or more processor cores and may be configured to executesystem software 210. System software 210 may include, for example,operating system code 212 (e.g., OS kernel code) and local area network(LAN) driver code 214. LAN driver code 214 may be configured to control,at least in part, the operation of the Ethernet controller 220operation, as will be described in greater detail below. System memory208 may include I/O memory buffers 216 configured to store one or moredata packets that are to be transmitted by, or received by, Ethernetcontroller 220. Chipset circuitry 206 may generally include “NorthBridge” circuitry (not shown) to control communication between theprocessor 204, Ethernet controller 220 and system memory 208. Also,chipset circuitry 206 may include “South Bridge” circuitry (not shown)to control I/O communications between the host system 202 and theEthernet controller 220. “South Bridge” circuitry may include I/O buscircuitry which may comply, or is compatible, with PCI-Expresscommunications protocol to provide communications between chipsetcircuitry 206 and the Ethernet controller 220.

Ethernet controller 220 may be logically and/or physically divided intoa transmit path 221A and a receive path 221B. The Ethernet controllermay generally include Ethernet media access control (MAC) circuitry 222and physical interface (PHY) circuitry 224. MAC circuitry 222 mayinclude transmit MAC circuitry 222A configured to assemble data to betransmitted into frames, or packets, that include destination and sourceaddresses along with network control information and error detectionhash values. MAC circuitry 222 may also include receive MAC circuitry222B configured to remove data from received frames and place the datain system memory 208. PHY circuitry 224 may include encoding circuitry240A configured to encode data packets and decoding circuitry 240Bconfigured to decode data packets. Encoding circuitry 240A and decodingcircuitry 240B may collectively be embodied as a processor (for example,a digital signal processor) configured to perform analog-to-digital anddigital-to-analog conversion, encoding and decoding of data, analogparasitic cancellation (for example, cross talk cancellation), andrecovery of received data. PHY circuitry 224 may also include transmit(Tx) circuitry 226 configured to transmit one or more data packets andreceive (Rx) circuitry 228 configured to receive one or more datapackets. Rx circuitry 228 may include phase lock loop circuitry (PLL,not shown) configured to coordinate timing of data reception. The PHYcircuitry 224 may be coupled to an Ethernet communications link 230. TheEthernet communications link 230 may comprise, for example, a mediadependent interface which may include, for example Category 6 (Cat6)Ethernet cable.

Transmit MAC circuitry 222A may include a controllable clock input 242and a controllable power input 244. Clock input 242 may generallyinclude a clock signal that controls the clocking of the MAC circuitry222A. Power input 244 may generally include a power supply signal tosupply power to one or more components of the MAC circuitry 222A.Similarly, Receive MAC circuitry 222B may include a controllable clockinput 246 and a controllable power input 248. Clock input 246 maygenerally include a clock signal that controls the clocking of the MACcircuitry 222B. Power input 248 may generally include a power supplysignal to supply power to one or more components of the MAC circuitry222B. Encoding circuitry 240A may include a controllable clock input 254and a controllable power input 256, and decoding circuitry 240B mayinclude a controllable clock input 258 and a controllable power input260. Transmit circuitry 226 may include a controllable clock input 262and a controllable power input 264. In one embodiment, clocking of thetransmit path 221A and receive path 221B may be independentlycontrolled. Also, in one embodiment, the power of transmit path 221A andreceive path 221B may be independently controlled.

The Ethernet controller 220 may be configured to exchange commands anddata with a link partner 232, via communications link 230. “Linkpartner” as used herein, means any device that is configured tocommunicate with the Ethernet controller 220 using an Ethernetcommunications protocol. In at least one embodiment, the link partner232 may include a switch, bridge, router and/or other Ethernetcontroller (which may be associated with a host system similar to hostsystem 202) that may be configured and operate in a manner consistentwith the description of the Ethernet controller 220 provided herein.

Ethernet controller 220 may be configured to transmit at least one datapacket to the link partner 232, or receive at least one data packet fromthe link partner 232. As stated, the Ethernet controller 220 may beconfigured to operate, at least in part, in an idle power state and anactive power state. In one embodiment, to transition into the idle statefrom the active data transmission power state, the Ethernet controller220 may be configured to control the clock input 242, 254 and/or 262. Totransition into the idle power state from an active data reception powerstate, the Ethernet controller 220 may be configured to control theclock input 246 and/or 258. To that end, the clock inputs 242, 254, 262,246 and/or 258 may be gated (clock gating) to turn the clock signal OFFto the corresponding circuitry.

To permit asymmetric power management, the clock inputs of the transmitpath circuitry may be controlled independently of the clock inputs ofthe receive path circuitry. This may allow, for example, the circuitryin that transmit path 221A to be in the idle power state while thecircuitry in the receive path 221B is in the active state (or,vice-versa). Clock gating, as used herein, may provide a mechanism toachieve idle power state, as defined herein, in which the powerconsumption of the circuitry that is clock gated is sufficient tomaintain an open link with the link partner 232 (via communications link230), but insufficient for the Ethernet controller 220 to transmit orreceive data. To transition from the idle power state to the activepower state, the Ethernet controller 220 may be configured to turn theclock signals 242, 254, 262, 246 and/or 258 to an ON state to permit,for example, the Ethernet controller 220 to transmit and/or receivedata.

Operations of the Ethernet controller 220 during data transmission anddata reception, in conjunction with other features of the system of FIG.2, are described below:

Tx Active Transition

As stated, the Ethernet controller 220 may be configured to transition,at least in part, from an idle power state to an active datatransmission power state to transmit data. To that end, the LAN drivercode 214, as may be executed by host processor 204, may be configured todetermine the presence of at least one data packet, as may be stored inthe I/O memory buffer 216, to be transmitted. The driver 214 maygenerate a transmit active control signal to control the Ethernetcontroller 220 to transition from the idle power state into an activedata transmission power state. The clock signals 242 may be applied tothe transmit MAC circuitry 222A, and clock signals 254 and 262 may beapplied to the encoding circuitry 240A and transmit circuitry 226,respectively. If the link partner 232 is configured in a similar manner,transmit circuitry 226 may be configured to generate a receive activecontrol signal to “wake up” the corresponding receive circuitry and MACcircuitry of the link partner 232 in order to prepare the link partner232 to receive data from the Ethernet controller 220. After a specifieddelay period (e.g., delay period 110 depicted in FIG. 1), the Ethernetcontroller 220 may begin to transmit data to the link partner 232.

Tx Idle Transition

As stated, the Ethernet controller 220 may be configured to transitionfrom an active data transmission power state to an idle power state. Tothat end, the LAN driver code 214, as may be executed by host processor204, may be configured to determine that there are no data packets readyfor transmission, for example, by monitoring the I/O memory buffer 216,to determine if the buffer is empty. The driver 214 may generate an idlecontrol signal to control the Ethernet controller 220 to transition fromthe active data transmission power state into the idle power state. Theclock signal 242 may be gated to the MAC circuitry 222A to permit theMAC circuitry 222A to drop to an idle power consumption mode. Likewise,clock signals 254 and/or 262 may be gated to the encoding circuitry 240Aand/or transmit circuitry 226, respectively, to permit the encodingcircuitry 240A and/or the transmit circuitry 226 to drop to an idlepower consumption mode. If the link partner 232 is configured in asimilar manner, transmit circuitry 226 may be configured to generate areceive idle control signal to transition the corresponding decodingcircuitry and MAC circuitry of the link partner 232 into an idle powerstate.

Rx Active Transition

The Ethernet controller 220 may also be configured to transition, atleast in part, from an idle power state to an active data receptionpower state to receive data from the link partner 232. To that end, thelink partner 232 may generate a receive active control signal to thereceive circuitry 228. To that end, while the decoding circuitry 240Band the receive MAC circuitry 222B may each be in an idle power state,the receive circuitry 228 may be in an active power state so that link230 between the PHY circuitry 224 and the link partner 232 remains open.The receive active control signal generated by the link partner 232 maycomprise a burst signal that can be received and recognized by thereceive circuitry 228. In response thereto, the PHY circuitry 224 maytransition the decoding circuitry 240B from an idle power state to anactive power state, and PHY circuitry 224 may also generate a receiveactive control signal to transition the receive MAC circuitry 222B froman idle power state to the active power state. To that end, the clocksignals 258 and 246 may be applied (e.g., ungated) to the encodingcircuitry 240B and MAC circuitry 222B, respectively, to permit the MACcircuitry 222B and decoding circuitry 240B to receive data from the linkpartner 232. After a defined delay period (e.g., delay period 110depicted in FIG. 1), the Ethernet controller 220 may begin to receivedata from the link partner 232. The data may be stored in the buffermemory 216.

Rx Idle Transition

As stated, the Ethernet controller 220 may be configured to transition,at least in part, from an active data reception power state to an idlepower state. To that end, PHY circuitry 224 may be configured to receivea receive idle control signal from the link partner 232. In responsethereto, the PHY circuitry 224 may transition the decoding circuitry240B from an active power state to the idle power state (which, as notedabove, may include clock gating of the decoding circuitry 240B). PHYcircuitry 224 may also generate a receive idle control signal totransition the receive MAC circuitry 222B from an active data receptionpower state to the idle power state.

The control signals exchanged between the Ethernet controller 220 andthe link partner 232, as described above, may include, for example,control frames generated by respective PHY circuitry that includeencoded signals to transition to the active power state or the idlepower state. Alternatively, the control signals may comprise analogburst signals having predefined characteristics that may be interpretedby respective PHY circuitry as control signals to transition into theactive power state or the idle power state. Further alternatively, suchcontrol signals may be generated by MAC circuitry 222 in the form of,for example, header or footer data within a data packet.

FIG. 3 depicts a flowchart 300 of exemplary data transmission operationsconsistent with the present disclosure. Operations may includedetermining if data packets are in memory and available fortransmissions 302. Operations may also include generating a transmitactive control signal to transition an Ethernet controller, at least inpart, from an idle power state to an active data transmission powerstate 304. If a link partner, coupled to the Ethernet controller issimilarly configured, operations may also include generating a receiveactive control signal to the link partner to cause the link partner totransition, at least in part, from an idle power state to an active datareception power state 306. Operations may also include transmitting datapackets to the link partner using a maximum negotiated speed 308. Oncethe data packets are transmitted, operations may further includegenerating an idle control signal to transition the Ethernet controllerfrom the active data transmission power state to the idle power 310.Again, if the link partner is similarly configured, operations may alsoinclude generating a receive idle control signal to the link partner tocause the link partner to transition from the active data receptionpower state to the idle power state 312.

FIG. 4 depicts a flowchart 400 of exemplary data reception operationsconsistent with the present disclosure. Operations may includereceiving, by an Ethernet controller, a receive active control signalfrom a link partner 402. Operations may also include transitioning, atleast in part and in response to the receive active control signal, theEthernet controller from an idle power state to an active data receptionpower state 404. Operations may also include receiving, by the Ethernetcontroller, data packets from the link partner 406. The data packets maybe stored in memory 408. Operations may also include receiving, by theEthernet controller, a receive idle control signal from the link partner410. Operations may also include transitioning, at least in part and inresponse to the receive idle control signal, the Ethernet controllerfrom the active data reception power state to the idle power state 412.

The foregoing description of idle power state in connection with anEthernet controller offer significant power savings over otherapproaches. FIG. 5A depicts a power profile graph 502 according to arate-shifting Ethernet communications technique, and FIG. 5B depicts apower profile graph 504 consistent with the present disclosure. Ingeneral, power consumption (energy consumption) may be expressed as thearea under the power curve, i.e.,

∫_(t 1)^(t 2)power(t) 𝕕t

Average power may be defined as energy consumption over a given timeinterval. As shown, the power profile 502 of the rate-shifting techniquestarts at a first power level 506 where data transmission or receptionis possible but at a relatively low bandwidth, for example 1/10^(th) or1/100^(th) the maximum rate, and, based on increased bandwidthutilization or other considerations, increases power to a second higherlevel 508 for faster data transmission or reception. Thus, the energyconsumption is defined as both the area under region 506 and underregion 508. In contrast, the power profile 504 according to the presentdisclosure, data is transmitted or received at a maximum availablespeed, as depicted as the area in regions 510 and 511. Once data istransmitted or received, the power is reduced to the idle power state108. The average power utilized by the rate shifting technique isgreater than the average power utilized by the active/idle toggletechnique of the present disclosure, especially when long-term usage isconsidered. Unexpectedly, the applicant herein has determined that whilethe operating power is greater at the fastest available speed, totalenergy consumption is reduced, by completing the transmission morequickly and transitioning to the idle power state after datatransmission or reception.

The foregoing examples are described in reference to power gating of oneor more components of the Ethernet controller to achieve an idle powerstate. In other embodiments, additionally or as an alternative to clockgating, the Ethernet controller may also be configured to discontinuepower (e.g., power gating) to the MAC circuitry 222 and/or the PHYcircuitry 224. While power gating may achieve the appropriate idle powerstate as defined herein, this technique may cause an additional delaybetween idle to active transition.

Ethernet controller 220 may also include I/O bus circuitry (not shown)to provide I/O communications between the Ethernet controller 220 andthe chipset circuitry 206 (such bus circuitry may comply with theaforementioned PCI-Express communications protocol). Ethernet controllermay also include MAC/PHY interface circuitry (not shown) configured toprovide I/O communications between the MAC circuitry 220 and the PHYcircuitry 224 (which may include, for example SGMII or XAUI).

Memory 208 and/or memory associated with the Ethernet controller 220(not shown) may comprise one or more of the following types of memory:semiconductor firmware memory, programmable memory, non-volatile memory,read only memory, electrically programmable memory, random accessmemory, flash memory, magnetic disk memory, and/or optical disk memory.Either additionally or alternatively, memory 208 and/or memoryassociated with the Ethernet controller 220 (not shown) may compriseother and/or later-developed types of computer-readable memory.Embodiments of the methods described herein may be implemented in acomputer program that may be stored on a storage medium havinginstructions to program a system to perform the methods. The storagemedium may include, but is not limited to, any type of disk includingfloppy disks, optical disks, compact disk read-only memories (CD-ROMs),compact disk rewritables (CD-RWs), and magneto-optical disks,semiconductor devices such as read-only memories (ROMs), random accessmemories (RAMs) such as dynamic and static RAMs, erasable programmableread-only memories (EPROMs), electrically erasable programmableread-only memories (EEPROMs), flash memories, magnetic or optical cards,or any type of media suitable for storing electronic instructions. Otherembodiments may be implemented as software modules executed by aprogrammable control device.

The Ethernet communications protocol, described herein, may be capablepermitting communication using a Transmission Control Protocol/InternetProtocol (TCP/IP). The Ethernet protocol may comply or be compatiblewith the Ethernet standard published by the Institute of Electrical andElectronics Engineers (IEEE) titled “IEEE 802.3 Standard”, published inMarch, 2002 and/or later versions of this standard.

As used herein, a “PHY” may be defined as an object and/or circuitryused to interface to one or more devices, and such object and/orcircuitry may be defined by one or more of the communication protocolsset forth herein. The PHY may comprise a physical PHY comprisingtransceiver circuitry to interface to the applicable communication link.The PHY may alternately and/or additionally comprise a virtual PHY tointerface to another virtual PHY or to a physical PHY. PHY circuitry 224may comply or be compatible with, the aforementioned IEEE 802.3 Ethernetcommunications protocol, which may include, for example, 100BASE-TX,100BASE-T, 10GBASE-T, 10GBASE-KR, 10GBASE-KX4/XAUI, 40 GbE and or 100GbE compliant PHY circuitry, and/or PHY circuitry that is compliant withan after-developed communications protocol.

“Circuitry”, as used in any embodiment herein, may comprise, forexample, singly or in any combination, hardwired circuitry, programmablecircuitry, state machine circuitry, and/or firmware that storesinstructions executed by programmable circuitry.

The terms and expressions which have been employed herein are used asterms of description and not of limitation, and there is no intention,in the use of such terms and expressions, of excluding any equivalentsof the features shown and described (or portions thereof), and it isrecognized that various modifications are possible within the scope ofthe claims. Accordingly, the claims are intended to cover all suchequivalents.

1. An Ethernet controller, comprising: at least one Media AccessController (MAC); at least one interface to at least one PHY; andcircuitry arranged to, when operational: cause generation of a signalfor a first link partner signaling a first low power state; enter thefirst low power state, the first low power state to cause a reduction inpower consumed by transmit circuitry during the first low power state;cause generation of a signal for the first link partner signaling end ofthe first low power state; await a first predefined period of time;after the first predefined period of time, cause transmission, in afirst active power state, of at least one Ethernet data frame to thefirst link partner, the first active power state being a higher powerconsumption state of the transmit circuitry than the first low powerstate; receive an indication of a signal of the first link partnersignaling a second low power state; enter the second low power state,the second low power state to cause a reduction in power consumed byreceive circuitry during the second low power state; receive anindication of a signal of the first link partner signaling end of thesecond low power state; and enter a second active power state, thesecond active power state being a higher power consumption state of thereceive circuitry than the second low power state and after a secondpredefined period of time, receive at least one Ethernet data frame fromthe first link partner.
 2. The Ethernet controller of claim 1, whereinthe transmit circuitry comprises at least one of the following: a10GBASE-T PHY and a 1000BASE-T PHY.
 3. The Ethernet controller of claim1, wherein the circuitry comprises circuitry arranged to, whenoperational, transfer Ethernet data frames at a data rate negotiatedbetween the Ethernet controller and the first link partner.
 4. TheEthernet controller of claim 1, wherein the circuitry arranged to, whenoperational, reduce power consumed by transmit circuitry during thefirst low power state comprises circuitry arranged to, when operational,clock gate.
 5. The Ethernet controller of claim 4, wherein circuitryarranged to, when operational, clock gate the transmit circuitry isindependently controlled of circuitry to clock gate the receivecircuitry.
 6. The Ethernet controller of claim 1, wherein the circuitryis arranged to, when operational, reduce power consumed by at least oneof the at least one PHYs during the first low power state.
 7. TheEthernet controller of claim 1, wherein the Ethernet controller does nottransmit an Ethernet data frame to the first link partner during thefirst low power state and the Ethernet controller does not receive anEthernet data frame from the first link partner during the second lowpower state.
 8. The Ethernet controller of claim 1, wherein thecircuitry is arranged to, when operational, reduce power consumed by anencoder during the first low power state.
 9. The Ethernet controller ofclaim 1, wherein the circuitry is arranged to, when operational, reducepower consumed by an decoder during the second low power state.
 10. TheEthernet controller of claim 1, further comprising circuitry arrangedto, when operational, receive a signal from a driver causing theEthernet controller to enter the first low power state.
 11. A systemcomprising: network controller circuitry arranged to, when operational:cause generation of a signal for a first link partner signaling a firstlow power state; cause generation of a signal for the first link partnersignaling end of the first low power state; await a first predefinedperiod of time; after the first predefined period of time, causetransmission of at least one Ethernet data frame to the first linkpartner; receive indication of a signal from a the first link partnersignaling a second low power state; receive indication of a signal fromthe first link partner indicating end of the second low power state; andafter a second predefined period of time, receive at least one Ethernetdata frame from the first link partner; wherein the network controllercircuitry comprises receive circuitry and transmit circuitry.
 12. Thesystem of claim 11, wherein the network controller circuitry comprisescircuitry arranged to, when operational: reduce power consumed by thetransmit circuitry during the first low power state; and reduce powerconsumed by the receive circuitry during the second low power state. 13.The system of claim 11, wherein the network controller circuitrycomprises: at least one media access controller (MAC); and at least oneinterface to a PHY.
 14. The system of claim 11, wherein the receivecircuitry comprises at least one of the following: a 10GBASE-T PHY and a1000BASE-T PHY.
 15. The system of claim 11, wherein the networkcontroller circuitry comprises circuitry arranged to, when operational,cause transfer of data at a data rate negotiated between the networkcontroller and the first link partner.
 16. The system of claim 15,wherein circuitry arranged to, when operational, reduce power consumedby transmit circuitry during the first low power state comprisescircuitry arranged to, when operational, clock gate.
 17. The system ofclaim 16, wherein circuitry arranged to, when operational, clock gatethe transmit circuitry is independently controlled of circuitry arrangedto, when operational, clock gate the receive circuitry.
 18. The systemof claim 11, wherein the circuitry arranged to, when operational, reducepower consumed by at least one of the at least one PHYs during the firstlow power state.
 19. The system of claim 11, wherein the networkcontroller does not transmit a data frame during the first low powerstate and the network controller does not receive a data frame duringthe second low power state.
 20. The system of claim 11, wherein thecircuitry is arranged to, when operational, reduce power consumed by anencoder during the first low power state.
 21. The system of claim 11,wherein the circuitry is arranged to, when operational, reduce powerconsumed by an decoder during the second low power state.
 22. The systemof claim 11, further comprising circuitry to receive a signal from adriver causing the network controller to enter the first low powerstate.
 23. The system of claim 11, further comprising: at least one hostprocessor; and at least one memory.
 24. A method, comprising, at anetwork controller: causing generation of a signal for a first linkpartner signaling a first low power state; causing entering of the firstlow power state, the first low power state to cause a reduction in powerconsumed by the transmit circuitry during the first low power state;causing generation a signal for the first link partner signaling end ofthe first low power state; causing awaiting a first predefined period oftime; after the first predefined period of time, causing transmission,in a first active power state, of at least one Ethernet data frame tothe first link partner, the first active power state being a higherpower consumption state of the transmit circuitry than the first lowpower state; receiving an indication of a signal of the first linkpartner signaling a second low power state; causing entering of thesecond low power state, the second low power state to cause a reductionin power consumed by the receive circuitry during the second low powerstate; receiving an indication of a signal of the first link partnersignaling end of the second low power state; and causing entering asecond active power state, the second active power state being a higherpower consumption state of the receive circuitry than the second lowpower state and after a second predefined period of time, receive atleast one Ethernet data frame.
 25. The method of claim 24, wherein thereceive circuitry comprises at least one of the following: a 10GBASE-TPHY and a 1000BASE-T PHY.
 26. The method of claim 24, further comprisingtransferring Ethernet data frames at a data rate negotiated between thenetwork controller and the first link partner.
 27. The method of claim24, further comprising reducing power consumed by transmit circuitryduring the first low power state comprises circuitry to clock gate. 28.The method of claim 24, further comprising clock gating the transmitcircuitry independently of clock gating of the receive circuitry. 29.The method of claim 24, further comprising reducing power consumed by atleast one of the at least one PHYs during the first low power state. 30.The method of claim 24, wherein the controller does not transmit anEthernet data frame during the first low power state and the controllerdoes not receive an Ethernet data frame during the second low powerstate.
 31. The method of claim 24, further comprising reducing powerconsumed by an encoder during the first low power state.
 32. The methodof claim 24, further comprising reducing power consumed by an decoderduring the second low power state.
 33. The method of claim 24, furthercomprising receiving a signal from a driver and in response causingentering of the first low power state.
 34. The method of claim 33,further comprising sending the signal from the driver based on an amountof data available in a data buffer.
 35. An article comprising anon-transitory storage medium having stored thereon instructions thatwhen executed by a processor results in the following: causinggeneration of a signal for a first link partner signaling a first lowpower state; causing entering of the first low power state, the firstlow power state to cause a reduction in power consumed by the transmitcircuitry during the first low power state; causing generation a signalfor the first link partner signaling end of the first low power state;causing awaiting a first predefined period of time; after the firstpredefined period of time, causing transmission, in a first active powerstate, of at least one Ethernet data frame to the first link partner,the first active power state being a higher power consumption state ofthe transmit circuitry than the first low power state; receiving anindication of a signal of the first link partner signaling a second lowpower state; causing entering of the second low power state, the secondlow power state to cause a reduction in power consumed by the receivecircuitry during the second low power state; receiving an indication ofa signal of the first link partner signaling end of the second low powerstate; and causing entering a second active power state, the secondactive power state being a higher power consumption state of the receivecircuitry than the second low power state and after a second predefinedperiod of time, receive at least one Ethernet data frame.
 36. Thearticle of claim 35, further comprising instructions that result inresponding to a signal from a driver and in response causing entering ofthe first low power state.
 37. The article of claim 35, furthercomprising instructions that result in sending the signal from thedriver based on an amount of data available in a data buffer.